Release 10.1A: OpenEdge Getting Started:
Installation and Configuration

Updating session types

In the "Editing the Progress Dynamics XML configuration file" section, you updated the session that you use to administer your Repository. You must now update any other session types that apply to your application.

From the Dynamics Administration Tool Session menu, access the Session Type Control and modify your existing session types. After modifying your session types, regenerate the XML configuration file. (You can also edit the configuration file manually, but manual editing is more error prone.) See OpenEdge Development: Progress Dynamics Administration for more information about defining, modifying, and managing sessions.

Note: If you did not create a new icfconfig.xml file (or edit the default) for your application, you can skip this section. You can simply use the standard icfconfig.xml file that ships with Progress Dynamics to access the upgraded Repository.

Modify your other session types as follows:

Remove the RVDB service from all session types that have it. It became obsolete in Version 2.0A. There should be no references to it in any of your session types.
Add the Reference Integrity Manager (RIManager) to all session types that make database connections. The manager’s filename is ry/app/ryrisrvrp.p.
Add the Customization Manager to all session types that make use of the customization facilities and all development session types and server-side (AppServer and WebSpeed) session types. The server side manager is ry/app/rycussrvrp.p and the client-side manager is ry/app/rycusclntp.p.
Add the RepositoryDesignManager to all development session types that construct objects and modify them using the AppBuilder toolset. The manager’s filename is ry/app/rydessrvrp.p.

The Repository Design Manager is only needed for development session types. It is not needed and should not be included in deployment sessions. It will only add unnecessary overhead when the application runs.

If you plan to deploy your application as a browser-based application on the Web, you must create an ICFWS session type. (See OpenEdge Development: Progress Dynamics Administration and OpenEdge Development: Progress Dynamics Web Development Guide for more information.) The ICFWS session type must include the following managers:

RequestManager (ry/app/ryreqsrvrp.p) — Handles requests coming in from a Web browser.
UserInterfaceManager (ry/app/ryuimsrvrp.p) — Handles the interactions with the user interface.

The following example shows entries for all the new managers as they appear in the XML configuration file:

<manager>     <cManagerName>RIManager</cManagerName>     <cFileName>ry/app/ryrisrvrp.p</cFileName>     <cHandleName>RI</cHandleName>     <cSuperOf/> </manager> <manager>      <cManagerName>CustomizationManager</cManagerName>      <cFileName>ry/app/rycussrvrp.p</cFileName>      <cHandleName>NON</cHandleName>      <cSuperOf/> </manager> <manager>      <cManagerName>RepositoryDesignManager</cManagerName>      <cFileName>ry/app/rydessrvrp.p</cFileName>      <cHandleName>NON</cHandleName>      <cSuperOf/> </manager> <manager>      <cManagerName>RequestManager</cManagerName>      <cFileName>ry/app/ryreqsrvrp.p</cFileName>      <cHandleName>NON</cHandleName>      <cSuperOf/> </manager> <manager>      <cManagerName>UserInterfaceManager</cManagerName>      <cFileName>ry/app/ryuimsrvrp.p</cFileName>      <cHandleName>NON</cHandleName>      <cSuperOf/> </manager>